from distutils.core import setup

setup(
    name='qmanager',
    description='\
QManager is an abstracted Django manager which filters via custom queries.',
    long_description="""\
The ``QManager`` class is a subclass of ``django.db.models.Manager`` which can
remove some of the boilerplate in manager definitions. Managers may be used to
define 'table-level' operations on your models, and one of their most common
uses is to provide a pre-defined ``QuerySet`` for model data. Typically, a
developer would subclass ``models.Manager`` and override its ``get_query_set``
method, replacing it with something to filter the default results by a certain,
hard-coded query.
The problem with this pattern is that it ends up being repeated several times
for each model as you try to define several useful custom managers for each
type of data. The ``QManager`` class abstracts this idiom by providing a simple
way of defining managers to return query sets, using the ``Q`` class in
Django's ORM, which aims to provide a way of defining custom SQL queries in
native Python code.""",
    version='0.2.1.0',
    author='Zachary Voase',
    author_email='cracka80@gmail.com',
    py_modules=['qmanager'],
    requires=['Django'],
    provides=['qmanager', 'django-qmanager'],
	classifiers=[
	'Development Status :: 3 - Alpha',
	'Framework :: Django',
	'Intended Audience :: Developers',
	'License :: OSI Approved :: BSD License',
	'Operating System :: OS Independent',
	'Programming Language :: Python',
	'Topic :: Internet :: WWW/HTTP :: Dynamic Content :: CGI Tools/Libraries',
	'Topic :: Software Development :: Libraries :: Python Modules']
)
